fix: Jump to correct column for class-level fixture definitions#7
Merged
Conversation
scan_fixtures was only storing the row, causing jump/fixture.lua to always land at column 0. For fixtures defined inside a class the def keyword is indented, so column 0 was wrong. Now stores col from func_node:start() and the jump uses it. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
scan_fixtureswas only storing the row of a fixture definition, causingjump/fixture.luato always land at column 0defkeyword is indented, so column 0 was wrongcolfromfunc_node:start()and the jump uses itTest plan
col=0for a top-level fixturecol=4for a fixture defined inside a class🤖 Generated with Claude Code